In-lane money transfer systems and methods

ABSTRACT

The present invention provides systems and methods to initiate, facilitate, process and/or perform money transfers. One such method includes receiving a request for a transfer pair verification from a vendor location ( 360 ), and verifying that the transfer pair is associated with a valid transfer pair record ( 362 ). The method includes sending the transfer pair verification to the vendor location ( 368 ), receiving a money transfer request ( 370 ) associated with the transfer pair from the vendor location, and authorizing a money transfer ( 372 ) to at least one of a first and second customers associated with the transfer pair. In this manner, a vendor location, which may include a point-of-sale device and may be a retail outlet (e.g., grocery store, gas station, or the like), can be used to facilitate a money transfer between two customers.

BACKGROUND OF THE INVENTION

The present invention relates generally to the field of money transfers, and in particular to the transfer of money between two frequent entities or customers which may occur using point-of-sale systems to initiate or facilitate the transfer.

Present money transfer procedures typically involve an individual going to a money transfer location, such as a Western Union location, and giving the customer service agent a variety of personal information. This personal information may include the names and addresses of the sender and recipient, proof of identification, and the amount to be transferred. This information is entered into a money transfer system, and used to create a record of the money transfer. Once the money to be transferred has been collected from the sender, the recipient then proceeds to a separate money transfer location, such as another Western Union location, to pick up the money. The recipient may be required to provide a money transfer number and/or proof of identification, prior to picking up the money. Typically, this procedure is followed for each subsequent money transfer, even when the sender and recipient are the same. As a result, people who frequently send money using money transfer systems are repeatedly providing much of the same information. Improvements are desired.

BRIEF SUMMARY OF THE INVENTION

The present invention relates generally to the field of money transfers, and in particular to the transfer of money between two frequent entities or customers which may occur using point-of-sale systems to initiate or facilitate the transfer. The present invention provides systems and methods to initiate, facilitate, process and/or perform money transfers. In one such embodiment, a method of processing money transfers includes receiving a request for a transfer pair verification from a vendor location, and verifying that the transfer pair is associated with a valid transfer pair record. The method includes sending the transfer pair verification to the vendor location, receiving a money transfer request associated with the transfer pair from the vendor location, and authorizing a money transfer to at least one of a first and second customers associated with the transfer pair. In this manner, a vendor location, which may include a point-of-sale device and may be a retail outlet (e.g., grocery store, gas station, or the like), can be used to facilitate a money transfer between two customers who have an established transfer pair record.

In one aspect, the method further includes establishing the transfer pair record associated with the first customer and the second customer. The transfer pair record may be established, for example, by verifying the identity of at least one of the first and second customers, receiving first and second customer information and creating a database record thereof, and providing a transfer pair code to at least one of the first and second customers. In some aspects, the transfer pair code is a string of alphanumeric characters. The transfer pair code also may include a money transfer recipient designator. For example, the code may have a prefix or suffix to indicate which of the two customers involved in the money transfer is the recipient.

In one aspect, the method includes sending a fee request to the vendor location. This may occur, for example, when the transfer pair verification is sent to the vendor location. The fee request may be a money transfer fee to be charged the customer initiating the money transfer. The fee may be a fixed fee (e.g., a set dollar amount per money transfer), or a variable fee (e.g., a percentage of the dollar amount being transferred).

In some aspects, the method includes receiving a payment record corresponding to the money transfer request. The payment record may be created by a point-of-sale device or a computer system associated with the vendor location. The payment record may indicate the amount to be transferred as requested by the customer. In other aspects, the transfer amount is fixed, and the record of this amount may further be stored in the transfer pair record. This feature may be useful, for example, if a customer wants to send a same amount each week, each pay period, each month, or the like.

The money associated with the money transfer request is dispensed to the first or second customer in some aspects. The dispensing may involve receiving a transfer pair code associated with the transfer pair from the first or second customer prior to the dispensing of the money. En this manner, the intended recipient provides the transfer pair code, and possibly other proof of identity, prior to receiving the transferred money.

The present invention further provides methods of facilitating money transfers by a customer. One such method includes receiving a money transfer request and a transfer pair code from a first customer. A request for a transfer pair verification is sent to a host computer, and the transfer pair verification is received from the host computer. If the verification is not received, in some aspects the money transfer request is denied. Alternatively, the money transfer may proceed after customer information is collected. The method includes receiving a payment from the first customer for transfer to a second customer associated with the transfer pair code, and sending a record of the money transfer request and the payment to the host computer. In some aspects, a receipt is provided to the first customer. In some aspects, at least a portion of the transfer occurs using a point-of-sale device or system. In other embodiments, some or all of the transaction occurs using a website interface, a voice recognition unit, a customer service representative, or the like. In this manner, transactions may occur between pre-registered entities (e.g., utility companies or other service providers), and/or between pre-registered customers (e.g., an individual), or sonic combination thereof, without needing to collect large amounts of data or information for each transaction.

Methods of the present invention will be particularly useful for initiating money transfers “in-lane,” such as while shopping at a retail outlet. In one aspect, the method further includes receiving a purchase request for a consumer item from the first customer. The payment includes a first payment portion associated with the consumer item and a second payment portion associated with the money transfer request. In some aspects, the payment further includes a third payment portion associated with a money transfer fee. In this manner, the customer can initiate the money transfer while attending to other shopping or errands, or while at a location not designated solely for money transfers. The use of a transfer pair, particularly a transfer pair previously established by the first and/or second customer, will reduce or eliminate the amount of personal information that otherwise would need to be collected prior to the money transfer. In some embodiments, the initiating customer need only provide the transfer pair and an amount to be transferred.

The present invention further provides systems to initiate, perform, process or otherwise facilitate money transfers. One such system includes a host computer having a processor coupled to a database. The host computer further includes code for performing various methods of the present invention. In one particular embodiment, the host computer includes code for receiving a request to verify a transfer pair from a point-of-sale device, code for verifying if the transfer pair is associated with a valid transfer pair record, and code for sending a transfer pair verification to the point-of-sale device. The host computer further includes code for receiving a money transfer request associated with the transfer pair from the point-of-sale device, and code for authorizing a money transfer to at least one of a first customer and a second customer associated with the transfer pair. In this manner, the money transfer may be initiated at a remote location, such as at a point-of-sale device. In some embodiments, the system includes the point-of-sale device.

In some aspects, the system further includes code for establishing the transfer pair record associated with the first customer and the second customer. The record may be established using code for receiving first and second customer information and creating a database record thereof to include a transfer pair code. The transfer code then is provided to at least one of the first and second customers.

Other objects, features and advantages of the present invention will become more fully apparent from the following detailed description, the appended claims, and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified depiction of a transfer pair record according to an embodiment the present invention;

FIG. 2 is a simplified schematic system for facilitating money transfers according to an embodiment of the present invention; and

FIGS. 3A and 3B are simplified flow diagrams of methods according to embodiments of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention includes systems and methods that initiate, facilitate, process and/or perform money transfers or other recurring financial transactions between two parties, entities, or customers. The embodiments of the present invention Will be particularly useful for customers who commonly send money to the same one or few number of recipients. For example, legal aliens working within the United States may use a money transfer system to send money back to their family in Mexico, or South or Central American countries. These money transfers may occur at fairly regular intervals, and may, for example, correspond to times at which the workers are paid by their employers. Some embodiments of the present invention will be particularly useful to reduce the amount of information these customers must provide each time they desire to send money. Further, the number of locations at which a money transfer can be initiated are increased through use of the systems and methods of the present invention.

In some embodiments, a transfer pair record 100 is created for a pair of customers. As shown in FIG. 1, in one embodiment transfer pair record 100 includes information on a first customer 110 and information on a second customer 120. The information includes the customers' names and addresses. Transfer pair record 100 may further include additional details on customers 110, 120 including, but not limited to, telephone numbers, cell phone numbers, email addresses, social security numbers, dates of birth, driver license numbers, employee identification numbers, passwords, credit card information, bank account information, information on other payment mechanisms, and the like. FIG. 1 depicts similar information for first customer 110 and second customer 120 within transfer pair record 100. In other embodiments, the amount of information for first and second customers 110, 120 may differ. For example, if second customer 120 is always going to be the money transfer recipient, the amount of information may be more or less than collected for first customer 110. Further, not all customers will have the same amount of personal information. For example, customers 110 and/or 120 may not have a valid driver's license, a U.S. Social Security number, an email address, or the like. Transfer pair record 100 will be particularly useful for first and second customers 110, 120 who want to send money to each other, or from one customer to the other, on more than one occasion.

Transfer pair record 100 is created a number of ways within the scope of the present invention. For example, first customer 110 may enter a money transfer location, such as a Western Union location, and provide relevant information to a customer service representative (CSR) for first customer 110 and second customer 120. This may occur, for example, when first customer 110 is the sender of money for transactions between these two customers. The CSR creates transfer pair record 100 by entering the collected information into a computer-based system having appropriate software. Transfer pair record 100 also may be created by allowing first customer 110 to enter customer information into a website, such as a Western Union website. In other embodiments, customer information is conveyed by telephone to a CSR or an interactive voice response (IVR) system, by mobile or wireless devices, or the like, in order to create transfer pair record 100. The amount of information retrieved from customers 110 and/or 120 may be effected by the Patriot Act, or other federal, state, or local legislation.

In a particular embodiment, first customer 110 and second customer 120 intend to transfer money between them, or from one of them to the other, on a regular or semi-regular basis. In some embodiments, first customer 110 is always the sender of the money and second customer 120 is always the recipient of the money. In other embodiments, second customer 120 sends money on some occasions, such as when they are paying back money loaned to them by first customer 110.

The creation of transfer pair record 100 includes, in one embodiment, the creation of a transfer pair code 140. Transfer pair code 140 may take a number of different forms within the scope of the present invention. As shown in FIG. 1, in one embodiment transfer pair code 140 includes a string of alphanumeric characters. In some embodiments, transfer pair code 140 includes a character, code segment, or the like that operates as a money transfer recipient designator. The designator may be a prefix and/or a suffix that is used to designate which of customers 110, 120 is sending the money and which is receiving it. For example, as shown in FIG. 1, the suffix “-A” may indicate that first customer 110 is sending money to second customer 120, while the suffix “-B” may indicate money is being transferred from second customer 120 to first customer 110. In other embodiments, transfer pair code 140 is completely different depending upon which of the customers 110, 120 is the initiator or recipient in the money transfer. In some embodiments, transfer pair codes 140 take alternative forms other than a string of alphanumeric characters. For example, transfer pair codes 140 may be embodied in a universal product code. (UPC) that is sent or provided to customers 110 and/or 120.

In some embodiments, it may be desirable for first customer 110 to send a prescribed amount of money to second customer 120. In this embodiment, transfer pair record 100 includes a transfer amount 130. This embodiment will be useful, for example, when first customer 110 wants to be sure they send the necessary amount to second customer 120. In other embodiments, the amount of each money transfer can vary. In one such embodiment, the variable amount is not maintained in transfer pair record 100. In another embodiment, a history of the transfers between first and second customers 110, 120 are maintained in transfer pair record 100.

While transfer pair record 100 is shown pairing two customers 110, 120, in some embodiments transfer pair record 100 is created for use with money transfers between more than two customers. For example, transfer pair record 100 may include information on a third customer, and may include additional transfer pair codes for the transfer of money to and/or from the third customer to first customer 110 and/or second customer 120. This embodiment may be useful, for example, if first customer 110 is a parent with two children in college. In this example, first customer 110 wishes to send money to their children (e.g., second customer 120 and third customer) at different points in time, at different locations (e.g., at different schools), in different amounts, and the like. In an alternative example, the third customer operates as a proxy for the second customer. For example, the second (money receiving) customer may be an elderly parent, with the third customer being their son or daughter. The son or daughter may be authorized to receive the money on the parent's behalf in certain prescribed situations (e.g., when the parent is ill) or, alternatively, in all circumstances. In this example, the third customer (son or daughter) also is registered, with the transfer pair record having information on the third customer.

In another embodiment, a “batch” of transactions may occur. For example, when a first customer receives their paycheck, they may want to send X dollars to their mother, Y dollars to their sister and Z dollars to their brother. A transaction record is created for this group of parties, so that each time the record identifier is used the above transactions occur. In some embodiments, the transaction record identifies the amounts and recipients as previously described. In other embodiments, the amount to be sent is calculated on a percentage basis. For example, the first customer may identify the total amount to be transferred, and the transaction record contains information that the mother receives, for example, fifty percent (50%), and each of the siblings is to receive twenty-five percent (25%) of the transfer amount. In other embodiments, the appropriate transaction fees are removed prior to distribution of the funds. In other embodiments, the-amounts can be dynamically managed, such as by electronic means (e.g., the Internet) to adjust the amounts, percentages, or the like. In some cases, if the first customer wants to send money only to their mother, a separate transaction pair for the first customer and mother is created if the customer desires recurring transfers.

In a preferred embodiment, the creation of transfer pair record 100 produces one or more transfer pair codes 140 that are unique to first customer 110 and second customer 120 associated with transfer pair record 100. Transfer pair codes 140 are then provided to one or both customers 110, 120. Providing transfer pair codes 140 to customers 110, 120 occurs through a variety of mechanisms within the scope of the present invention. For example, transfer pair code 140 may be provided to first customer 110 when they create transfer pair record 100. In another embodiment, transfer pair codes 140 are mailed to one or both customers 110, 120 in a fashion similar to the mailing of a personal identification number (PIN) commonly used with automated teller machine (ATM) cards. In another embodiment, transfer pair codes 140 are emailed to customers 110, 120 using, for example, the email addresses entered into transfer pair record 100. In still another embodiment, transfer pair codes 140 are embodied or printed on a presentation device, such as a card or the like. The presentation device is sent or provided to customers 110, 120. In one embodiment, the presentation device is a card containing a magnetic stripe. Transfer pair code(s) 140 may be encoded in the magnetic stripe along with, in some embodiments, additional information from transfer pair record 100. Customers 110, 120 can use the presentation device when they send or receive money as further described below. It will be appreciated by those skilled in the art that the form of transfer pair code. 140 and the method at which transfer pair codes 140 are provided to customers 110 and/or 120 may vary within the scope of the present invention beyond the above specific examples.

Once transfer pair record 100 has been established, transfer pair code 140 can be used to initiate money transfers from a variety of locations. In some embodiments, customer 110 or 120 initiates the money transfer by logging onto a money transfer organization website, such as the Western Union website. Transfer pair code 140 is entered into the website so that the Western Union money transfer system accesses transfer pair record 100 associated with the appropriate customers 110, 120. In this embodiment, the website may prompt the customer to provide further information such as a date of birth, a driver's license number, a password, or the like, to verify that the individual interfacing with the website is indeed one of first or second customers 110, 120. The initiation of money transfers using transfer pair code 140 also may occur by telephone, by interfacing with an IVR system, or the like. For example, first customer 110 may call a customer service representative (CSR) associated with the organization facilitating the money transfers (e.g., Western Union). First customer 110 provides the CSR with transfer pair code 140, a transfer amount (if the transfer pair allows variable amounts), and a payment method. In some embodiments, additional authorization also is provided (e.g., a password or other information in transfer pair record 100) by first customer 110. In some embodiments, the acceptable payment method is limited to payment methods already identified in transfer pair record 140 (e.g., a credit card account, Paypal account, etc.). In some embodiments, a receipt for the transaction is provided to first customer 110, such as by email, voice message, paper receipt mailed to first customer 110's address, or the like. A particular advantage of the present invention further includes the use of transfer pair codes 140 while customers 110 and/or 120 are at a retail location as will be further described in conjunction with subsequent figures.

Turning now to FIG. 2, a system 200 for initiating, facilitating, processing and/or performing money transfers according to embodiments of the present invention will be described. System 200 includes a host computer system 240 coupled to a database 242. In one embodiment, host system 240 comprises a server or other computer based apparatus for creating and maintaining records associated with money transfers. Host computer system 240, in one embodiment, is operated by a third party such as Western Union or another money transfer organization. Database 242 maintains records of money transfers. Further, in one embodiment, database 242 maintains some or all transfer pair records 100. For example, host computer system 240 may comprise or be coupled to a server maintaining a Western Union website into which first customer 110 inputs data to create transfer pair record 100. Similarly, host computer system 240 may have other user interfaces by which a customer service representative enters data and creates transfer pair records 100. Further, host computer system 240 may include or be coupled to an interactive voice response system to allow customer 110 to interface with system 240 to create transfer pair records 100.

In one embodiment, a transfer pair record has been created for a first customer 260 and a second customer 280. In this embodiment, second customer 280 is the intended recipient of a money transfer initiated by first customer 260. In order to receive the money, second customer 280 goes to a remote terminal or system 250. Remote system 250 may be a kiosk, a money transfer location such as a Western Union location, or the like. In alternative embodiments, the transferred money is deposited into a permanent or temporary account for second customer 280, such as a bank account, a stored value account, or the like. In one embodiment, remote system 250 also comprises a computer system, associated databases (not shown), and other necessary hardware and software in order to help coordinate the money transfers for customers 260 and 280. In one embodiment, remote computer system 250 is coupled to host computer system 240 so that database records maintained in database 242 are accessible by remote computer 250. This coupling between remote system 250 and host computer system 240 may be a direct coupling or may be a coupling through a network 230 as depicted in FIG. 2. Network 230 may include telephone networks, credit card networks, wide area networks, the Internet, wireless networks, and the like. Further, depending on the type of processing device used to transmit the information, such devices may also be coupled to a financial network such as a credit card network or Automated Teller Machine (ATM) network, or may have a direct connection to other host computer systems.

While host computer system 240 is depicted as a single system, host computer system 240 may have multiple components and may comprise a collection of more than one system. For example, money transfer records may be maintained in a first portion of host computer system 240, while transfer pair records 100 may be maintained in a second portion of host computer system 240. Multiple databases 242 also may be used to facilitate the storage and retrieval of transfer pair records 100.

In some embodiments, portions of system 200 are found in retail outlets, such as grocery stores, gas stations, and the like. In one embodiment, a retail outlet has an associated vendor system 220 coupled to a database 222. Vendor system 220 also is coupled to a point-of-sale (POS) device or terminal 210. In some embodiments, POS device 210 is a point-of-service, such as a location at which the customer receives some service or benefit as opposed to making physical purchases. The coupling between vendor system 220 and terminal 210 may be a direct coupling, or may be an electronic coupling through network 230. A direct coupling between vendor system 220 and point-of-sale device 210 may comprise, for example, a point-of-sale terminal 210 in a store location, physically or wirelessly coupled with vendor system 220. In some embodiments, vendor system 220 comprises a server, a computer, or the like, which maybe located in a back room of the store or retail location.

Vendor system 220 and its associated database 222 may contain a wide variety of store-related records. For example, in sonic embodiments database 222 contains inventory lists, price lists, vendor lists, employee information and the like. In a particular embodiment, point-of-sale device 210 exists in a grocery store having a plurality of items available for consumers to purchase. Typically, such a point-of-sale device forms part of a cash register system in which the customer, or a clerk or employee of the store, scans item UPC's or item information into point-of-sale device 210. Point-of-sale device 210 receives the costs associated with those items from vendor system 220, or alternatively the costs are maintained in POS device 210 by a SKU, etc. Point-of-sale device 210 then accumulates a total cost of all items to be purchased by first customer 260 and presents the total to customer 260. First customer 260 will then tender payment for the desired items and depart the store location. If the payment is rendered using a credit card, a personal check, or the like, a payment authorization process may occur before the customer departs with the desired items. This authorization may involve standard credit card authorization or check authentication as known to those skilled in the art. Customer 260 also may pay by cash, money order, travelers check, or the like.

In some embodiments, vendor system 220 does not reside at a store location, but instead resides at a regional location. For example, a grocery store chain may have a single regional vendor system 220 maintaining records of store inventory, and costs and prices associated with items sold therein. The point-of-sale terminals 210 in one or more store locations are coupled to vendor system 220. In this manner, inventory and prices can be managed on a regional level in addition to a store by store manner. In still another embodiment, vendor system 220 is a third party owned system used to facilitate various transactions. In some cases, vendor system 220 resides at a third party transaction processing facility.

In some embodiments, point-of-sale terminals) 210 communicate with vendor system 220 through network 230. Point-of-sale devices 210 that may be used to capture, transmit and/or receive information to and from host computer system 220 for some. embodiments of the present invention are further described in copending U.S. application Ser. No. 10/116,689, entitled Systems and Methods for Performing Transactions at a Point-of-Sale, filed Apr. 3, 2002, and assigned to the assignee of the present invention, the complete disclosure of Which is herein incorporated by reference.

In some cases first customer 260 purchases items at the store using the above-noted procedure, but also wants to initiate a money transfer to second customer 280. In some embodiments of the present invention, system 200 is adapted to allow first customer 260 to initiate a money transfer at the store location using point-of-sale terminal 210. In a particular embodiment, customer 260 presents a money transfer request to either point-of-sale terminal 210 or a clerk operating point-of-sale terminal 210. In doing so, first customer 260 provides the clerk or POS device 210 with transfer pair code 140 associated with first customer 260 and the correct second customer 280 to whom first customer 260 is sending money. This may be a verbal rendering, from which the clerk or customer 260 will key in the appropriate transfer pair code and/or the requested money transfer amount into point-of-sale terminal 210. In another embodiment, transfer pair code 140 has been printed on a piece of paper and provided to the clerk. The printed paper may be a handwritten transfer pair on a money order request sheet obtained by first customer 260 at the vendor location, an email first customer 260 received from host system 240 which first customer 260 has printed and carried with them to the store, or the like. In another embodiment, the store has a kiosk, a computer, or the like which is coupled to host system 240. In this manner, first customer 260 can retrieve their transfer pair code 140 while at the store for initiating the money transfer. Alternatively, some or all of transfer pair code 140 or other customer account information is maintained on a presentation device 270, such as in a Universal Product Code (UPC). Alternatively, a magnetic strip may be provided on presentation device 270 having transfer pair code 140 and possible additional information as well. Information maintained in UPC, the magnetic strip, written or printed on presentation device 270, or the like, may include the customer name, money transfer amount 130, transfer pair code 140, and the like.

Transfer pair code 140 is entered into POS device 210, and transmitted to host computer 240. Host computer 240 checks the received transfer pair code 140 against transfer pair records 100, including records 100 which may be stored in database 242. In some embodiments, a customer name or other information is sent to host computer 240, and checked against the transfer pair record corresponding to the provided transfer pair code 140. Host system 240 may confirm, for example, that the provided transfer pair 140 corresponds to a valid transfer pair record 100. For a verified transfer pair code 140, host system 240 returns a money transfer authorization or transfer pair code verification to POS device. 210. POS device 210, or the clerk operating POS device 210, then proceeds with the money transfer by collecting the money to be transferred from customer 260. For fixed amount transfers, in some embodiments the money transfer authorization may include the money transfer amount. In this manner, POS device 210 is informed of the authorized money transfer it may collect. In other embodiments, the money transfer authorization returns a maximum money transfer amount. In this case, POS device 210 is authorized to accept money transfers up to the maximum authorized amount, but not a greater amount.

In some embodiments, the money transfer amount is collected from customer 260, and any money transfer fees are deducted from the collected amount. In other embodiments, POS device 210 is instructed by host system 240 to collect a money transfer fee in addition to the money transfer amount customer 260 wishes to transmit. In some embodiments, the money transfer fee is a variable amount such as a percentage of the money transfer amount. The collection of the fee would be similar to applying a sales tax to an item being purchased at POS device 210. In other embodiments, the money transfer fee is a fixed amount (e.g., five dollars per transfer). Additional money transfer fees may he used in alternative embodiments, such as a sliding fee scale (e.g., a five dollar fee for every one hundred dollars transferred, with a maximum fee of fifty dollars). In some embodiments, the transfer pair verification response sent to POS device 210 includes the money transfer fee to be collected. In other embodiments, presentation device 270 and/or vendor system 220 maintains a money transfer fee schedule. The money transfer fee may include a fee to be paid the operator of host system 240, and may include a fee to be paid to the operator of vendor system 220.

In one embodiment, host system 240 and associated database 242 maintains some or all of the transfer pair records 100. In this embodiment, point-of-sale terminal 210 communicates via network 230 to host computer 240 in order to facilitate money transfers. In one embodiment, appropriate software is maintained on host computer 240 and/or remote computer 250 or their associated databases 242, to perform the money transfer process. Additional details on some methods according to the present invention will be further described in conjunction with FIGS. 3A and 3B.

When customer 260 tenders payment for items purchased at the store and/or for a money transfer, this payment may require further authorization. For example, if customer 260 is paying with a credit card, a standard credit card authorization may be performed using point-of-sale terminal 210. Similarly, if customer 260 is paying with a personal check, a check authentication process may be performed at point-of-sale terminal 210. In some embodiments, customer 260 will be tendering payment only for the money transfer. In other embodiments, customer 260 will be tendering payment for the money transfer and also additional items purchased at the store location operating point-of-sale terminal 210. In this manner, customer 260 may kill two birds with one stone by, for example, purchasing desired groceries or other items available at a store as well as initiating a money transfer.

In some embodiments, payment received by point-of-sale terminal 210 for money transfers is forwarded to host system 240 using an Automated Clearing House (ACH) system and process, the Western Union Money Transfer System, or another money transfer system. In some embodiments, host computer 240 controls or helps control the ACH process for payments received from customer 260 that are associated with money transfers. In this manner, host computer 240 may control the money transfer process so that money collected by point-of-sale terminal 210 is made available to second customer 280 associated with transfer pair record 100 that they share with first customer 260. Additional details on money transfers for use with the present invention may be found in U.S. application Ser. No. 10/206,661, filed Jul. 26, 2002, entitled Money Transfer Systems and Methods for Travelers, and assigned to the assignee of the present, the complete disclosure of which is herein incorporated by reference.

Turning now to FIGS. 3A and 3B, methods of the present invention will be described. In particular, FIG. 3A depicts a method 300 for facilitating a money transfer by a customer. FIG. 3B depicts a method 350 for processing a money transfer. As shown in FIG. 3A, method 300 includes receiving a request for a money transfer (Block 310) and receiving a transfer pair code (Block 312). In some embodiments, receipt of the money transfer request and the transfer pair code occur simultaneously, and in still other embodiments, the receipt of the transfer pair code comprises the money transfer request. The receipt of the money transfer request and transfer pair code may occur according to any of the above described methods. For example, the transfer pair code may be embodied in a UPC or in a magnetic stripe on presentation device 270 that is received by point-of-sale device 210 or a clerk operating point-of-sale device 210. Method 300 includes requesting a verification of the transfer pair (Block 314). This verification request may include point-of-sale device 210 and/or vendor system 220 sending a request to host system 240 to verify the transfer pair. Method 300 includes determining whether the transfer pair has been verified (Decision Block 316). In one embodiment, POS device 210 receives a “YES” verification or a “NO” verification response from host 240. If the transfer pair is not verified, the money transfer request is terminated (Stop 318). If the transfer pair is verified, method 300 includes receiving payment for the money transfer (Block 320). Payment may involve a money transfer customer paying cash, or the like, to POS device 210 or a clerk operating POS device 210.

Receipt of payment may further include receiving payment of a money transfer fee. In some embodiments, the money transfer fee is deducted from the money transfer amount requested. In other embodiments, the customer initiating the transfer pays the amount they desire to transfer to the recipient, and also pays a money transfer fee. Thus, receiving payment may have multiple components. Payment may also include a payment portion for the customer's purchase of various consumer items or services at a retail location operating POS device 210. Method 300 includes sending a record that the money transfer has been successfully initiated and that the money has been collected (Block 322). Again, point-of-sale device 210 and/or vendor system 220 may send the record to host computer system 240. Database 222 may store a record of the money transfer request being processed. Method 300 includes sending of the payment (Block 324), which may include the actual transmission of money, or the transmission of payment records through an ACH or other system. In some embodiments, method 300 is largely completed by using point-of-sale device 210 and/or vendor system 220.

FIG. 3B depicts method 350 for processing a money transfer request. Method 350 includes receiving a request for a transfer pair verification (Block 360). As noted above, this request may be received by host system 240 from point-of-sale device 210 and/or vendor system 220. Method 350 includes attempting to verify the transfer pair (Block 360). Host system 240 accomplishes this process, in some embodiments, by comparing the received transfer pair code 140 with the transfer pair records 100. In some embodiments, host system 240 also compares a customer name received from POS device 210 with customer names contained in the transfer pair record 100 associated with the received transfer pair code 140. If the transfer pair is not verified (Decision Block 364) a denial may be returned to the money transfer requestor (Block 366). The denial maybe transmitted to point-of-sale device 210 and/or vendor system 220 for relay to the customer requesting the money transfer. A denial may occur for a variety of reasons, including without limitation, an incorrect transfer pair code, an incomplete transfer pair record 100 associated with transfer pair code 140, a message or notice placed in transfer pair record 100 indicating further money transfers should be denied, or the like. In some embodiments, transfer pair 140 is verified and a verification is returned by host system 240 (Block 368).

Method 350 includes receiving the money transfer request (Block 370). This may, for example, comprise host system 240 receiving a notification from point-of-sale device 210 and/or vendor system 220 that the customer associated with the transfer pair verification has indeed paid for the money transfer. Receipt of the money transfer request may include receiving additional information, such as the transfer pair code that in turn identifies the sending and receiving customers, and the amount to be transferred in the event the transfer pair record allows variable transfer amounts. In some embodiments, method 350 further includes authorizing the transfer (Block 372). Authorizing the transfer may include host system 240 creating or maintaining a record that customers associated with the verified transfer pair have initiated a money transfer in a designated amount (fixed or variable) and that the money may be dispensed to second customer 280 upon proof of identity. As shown in FIG. 2, second customer 280 receives the money from a remote system 250, that in turn is coupled to host system 240. In some embodiments, system 240 makes the money available to second customer 280 only after a period of time has passed since first customer 260 paid. In this manner, non-cash payments made by first customer 260 for the money transfer can be approved or confirmed before dispensing the cash to second customer 280.

The advantages of the present invention, including the examples described in conjunction with FIGS. 1-3, are numerous. For the consumer, the consumer now has multiple locations at which they can initiate a money transfer. The consumer may multi-task by sending money from a location at which they had already planned to purchase groceries or the like. Further, the customer need not repeatedly provide all of the information typically needed for a money transfer as most or all of the information is maintained in the transfer pair record.

Benefits to the host system are numerous as well. For example, point-of-sale device 210 can facilitate payment authorization through the credit card authorization and check authentication processes. The money transfer host system will receive payments quickly from the vendor through the ACH or other money transfer processing system. In some embodiments, however, money transfer payments are made in cash, by cashiers check, or other certified funds. The host system operator further benefits by having customers who are satisfied at having additional locations at which a money transfer may be initiated and paid for. Host system 240 operator also benefits by not having to enter a complete data set for its frequent customer each time the customer wants to send money.

Benefits to the vendor operating point-of-sale device 210 also exist. First, the vendor, by participating in this process, is providing an additional service to customers which their competitors may not. This could increase consumer traffic to their store locations. For example, while the above examples describe the user proceeding to a grocery store to purchase items and at the same time initiating a money transfer, the reverse may happen. For example, the user may proceed to the grocery store to initiate a money transfer, and while they are there purchase a few items. In addition to the possibility of additional purchases, increased revenue may be received by the merchant through commissions paid by the customer and/or the money transfer host. In one embodiment, the vendor receives a small fee from the host for each money transfer initiated from the vendor location. Still another advantage to the vendor would be the float available to the vendor. The vendor may have in their account the money associated with the money transfers paid by their customers for a period of time before transmission of the money to the host. It will be appreciated by those skilled in the art that additional benefits to each of the parties of the methods of the present invention, arising from one or more components of the systems of the present invention may be realized within the scope of the present invention.

The invention has now been described in detail. However, it will be appreciated that the invention may be carried out in ways other than those illustrated in the aforesaid discussion, and that certain changes and modifications may be practiced within the scope of the appended claims. Accordingly, the scope of this invention is not intended to be limited by those specific examples, but rather is to be accorded in the scope represented in the following claims. 

1.-20. (canceled)
 21. A system for processing money transfers, the system comprising: a vendor system communicatively coupled to a point of sale device and a host computer, wherein the vendor system is configured to: receive, from the point of sale device, a request for verification of a transfer pair code; send the request for verification of the transfer pair code to the host computer; receive a verification of the transfer pair code from the host computer; send the verification of the transfer pair code to the point of sale device; receive a money transfer request associated with the transfer pair code from the point of sale device; send the money transfer request to the host computer; receive an authorization for the money transfer from the host computer; and send the authorization for the money transfer to the point of sale device.
 22. The system as in claim 21, wherein the vendor system is further configured to: receive, from the point of sale device, payment information associated with the money transfer request, wherein the payment information comprises a payment from a first customer for transfer to a second customer associated with the transfer pair code; receive a record of the money transfer request from the point of sale device; and send the payment information and the record of the money transfer request to the host computer.
 23. The system as in claim 21, wherein the vendor system is further configured to: receive the transfer pair code from the point of sale device, wherein the transfer pair code identifies a sender of money transfer funds and a receiver of money transfer funds; and send the transfer pair code to the host computer.
 24. The system as in claim 23, wherein the transfer pair code comprises a recipient designator that identifies the sender and receiver.
 25. The system as in claim 23, wherein the transfer pair code is associated with either or both a magnetic stripe or a Universal Product Code (UPC) of a presentation instrument.
 26. The system as in claim 21, wherein the vendor system is further configured to receive a payment from a first customer at the point of sale device, wherein the payment comprises: a first payment portion comprising an amount of money to transfer from the first customer to a second customer associated with the transfer pair code; a second payment portion comprising a fee for the money transfer; and a third payment portion that comprises an amount of money to pay for one or more goods or services purchased by the first customer at the point of sale device.
 27. The system as in claim 21, wherein the vendor system is located at a transaction processing facility and the vendor system is associated with an entity other than the entities associated with the host computer and the point of sale device.
 28. The system as in claim 21, wherein the vendor system is further configured to store information associated with the money transfer request in a database communicatively coupled with the vendor system.
 29. The system as in claim 21, wherein the authorization for the money transfer received from the host computer comprises a maximum money transfer amount that authorizes the point of sale device to accept funds for the money transfer up to the money transfer amount.
 30. A method for processing money transfers, the method comprising: receiving, from a vendor location, a request for a transfer pair verification; verifying the transfer pair is associated with a valid transfer pair record; sending the transfer pair verification to the vendor location; receiving a money transfer request associated with the transfer pair from the vendor location, wherein the money transfer request identifies a sender of funds and a receiver of the funds; and authorizing a money transfer associated with the transfer pair.
 31. The method as in claim 30, wherein the transfer pair verification and the money transfer request are received simultaneously.
 32. The method as in claim 31, wherein the transfer pair verification comprises the money transfer request.
 33. The method as in claim 30, wherein the transfer pair verification is received before the money transfer request.
 34. A method for processing money transfers, the method comprising: receiving, from a vendor location, a request for verification of a transfer pair code, wherein the transfer pair code identifies at least one of a sender of funds and a receiver of the funds; verifying the transfer pair code is associated with a valid transfer pair record, wherein the transfer pair record is associated with at least one of the sender and the receiver; sending the transfer pair code verification to the vendor location; receiving a money transfer request associated with the transfer pair code from the vendor location; and authorizing a money transfer from the sender to the receiver.
 35. The method as in claim 34, wherein the transfer pair code comprises a recipient designator that indicates the at least one of the sender and the receiver, and wherein the recipient designator is variable so that the at least one of the sender and the receiver may be varied depending on the recipient designator used.
 36. The method as in claim 34, wherein receiving the transfer pair code comprises receiving transfer pair code information obtained from reading a presentation device.
 37. The method as in claim 36, wherein reading a presentation device comprises reading at least one of: a magnetic stripe; and a Universal Product Code (UPC).
 38. The method as in claim 34, further comprising: establishing the transfer pair record; and associating at least one of the sender and the receiver with the transfer pair record.
 39. The method as in claim 38, wherein establishing the transfer pair record comprises: verifying the identity of at least one of the sender and the receiver; receiving information for at least one of the sender and the receiver and creating a database record thereof; and providing a transfer pair code to at least one of the sender and the receiver.
 40. A method of processing money transfers, the method comprising: receiving, from a vendor system, a request for a transfer pair verification; verifying the transfer pair is associated with a valid transfer pair record; sending the transfer pair verification to the vendor system for routing to a point of sale device; receiving a money transfer request associated with the transfer pair from the vendor system; and authorizing a money transfer to at least one of a first and second customers associated with the transfer pair. 